Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Increase timeouts for macOS toolchain setup #17519

Conversation

keith
Copy link
Member

@keith keith commented Feb 16, 2023

This switches all macOS toolchain setup compiles and executes to use the default timeout of 600s. This should help avoid issues on GitHub actions where these timeout and cause build failures. The common case shouldn't really be affected.

#17437

This switches all macOS toolchain setup compiles and executes to use the
default timeout of 600s. This should help avoid issues on GitHub actions
where these timeout and cause build failures. The common case shouldn't
really be affected.

bazelbuild#17437
@keith keith mentioned this pull request Feb 16, 2023
@keith
Copy link
Member Author

keith commented Feb 16, 2023

@susinmotion wdyt about us doing this, if we land here we can cherry pick to the 6.x branch before this is removed from bazel as well

@susinmotion
Copy link
Contributor

I think the change that just landed (causing those merge conflicts) allows it to be set by an env variable. Think that'll do the trick?

@keith
Copy link
Member Author

keith commented Feb 16, 2023

yea probably fine, might still be nice to bump the default so folks don't have to do any work to get the fix, but we can roll with that for now. I submitted a cherry pick for that here #17521

@keith keith closed this Feb 16, 2023
@keith keith deleted the ks/increase-timeouts-for-macos-toolchain-setup branch February 16, 2023 20:05
@susinmotion
Copy link
Contributor

Ah yeah that's a good thought re: default. That's fine with me.

copybara-service bot pushed a commit that referenced this pull request Mar 1, 2023
This should help avoid timeouts without users having to manually override this value. They can manually override it if they want to bring it down

#17519

Closes #17522.

PiperOrigin-RevId: 513258515
Change-Id: I2621b697643d4a1d6dc9db8ccee521f9ba0ce3dd
fweikert pushed a commit to fweikert/bazel that referenced this pull request May 25, 2023
This should help avoid timeouts without users having to manually override this value. They can manually override it if they want to bring it down

bazelbuild#17519

Closes bazelbuild#17522.

PiperOrigin-RevId: 513258515
Change-Id: I2621b697643d4a1d6dc9db8ccee521f9ba0ce3dd
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants